-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save the subresults for tmt-report-result #3200
Merged
Merged
+395
−102
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seberm
added
enhancement
area | results
Related to how tmt stores and shares results
labels
Sep 9, 2024
seberm
force-pushed
the
feature/save-subresults
branch
from
September 9, 2024 20:24
e927a18
to
3c0f414
Compare
seberm
commented
Sep 9, 2024
seberm
force-pushed
the
feature/save-subresults
branch
from
September 10, 2024 13:41
3c0f414
to
21f4b42
Compare
seberm
commented
Sep 10, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tried to change the method docstrings, releases.rst
and report-result.fmf
story to reflect the subresults feature. Are there any other places where I should document this feature?
Let me know if you need any further adjustments / tests. Thanks.
seberm
force-pushed
the
feature/save-subresults
branch
2 times, most recently
from
September 16, 2024 09:36
918ef90
to
70d2fcf
Compare
/packit build |
seberm
force-pushed
the
feature/save-subresults
branch
3 times, most recently
from
September 17, 2024 13:51
794f4fb
to
701b4de
Compare
seberm
force-pushed
the
feature/save-subresults
branch
2 times, most recently
from
September 17, 2024 14:48
387636a
to
821c8e1
Compare
seberm
requested review from
psss,
lukaszachy,
thrix and
janhavlin
as code owners
September 17, 2024 15:01
seberm
force-pushed
the
feature/save-subresults
branch
from
September 18, 2024 11:08
821c8e1
to
39181f9
Compare
seberm
force-pushed
the
feature/save-subresults
branch
3 times, most recently
from
September 25, 2024 15:41
428d10b
to
9dff2f8
Compare
seberm
force-pushed
the
feature/save-subresults
branch
from
September 30, 2024 08:35
9dff2f8
to
7381161
Compare
seberm
force-pushed
the
feature/save-subresults
branch
from
October 24, 2024 12:16
2bd4470
to
a93fcc5
Compare
happz
approved these changes
Oct 24, 2024
happz
added
the
status | ready for merge
The only missing piece is to do the rebase the current 'main' and let the CI finish.
label
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area | results
Related to how tmt stores and shares results
ci | full test
Pull request is ready for the full test execution
priority | must
high priority, must be included in the next release
status | ready for merge
The only missing piece is to do the rebase the current 'main' and let the CI finish.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All the results generated by
tmt-report-results
become objects oftmt.result.SubResult
and they get assigned under a parenttmt.Result
. Also, set theTESTID
andBEAKERLIB_COMMAND_REPORT_RESULT
test environment variables, so every call of beakerlib'srlPhaseEnd
macro becomes a subresult.Related to:
Blocked by:
data-path
field fromtmt-report-result
output #3270TODOs:
tmt-report-result -o <file>
result: restraint
? -> No. The subresults for test marked withresult: restraint
will be handled the same way as before (they get converted to "main" tmt custom results). The new thing here is that beakerlib phases are now also interpreted as tmt subresults. This means that in combination withresult: restraint
, the phases get also converted as main tmt custom results.tmt-report-result
gets called and log file is provided as a third argument (rstrnt-report-result: TESTNAME TESTRESULT LOGFILE [METRIC]
supports that). With-o
everything works as expected. Is this a bug?tmt-report-result
is our interface, we implement whatever we need to be there in a form we prefer and think is the best suited for the task of reporting results to tmt, and that comes with a set of options - it's not a 1:1 replacement forrstrnt-report-result
.Pull Request Checklist